chore(deps): update dependency wrangler to v3.16.0 #491
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.15.0
->3.16.0
Release Notes
cloudflare/workers-sdk (wrangler)
v3.16.0
Minor Changes
102e15f9
Thanks @Skye-31! - Feat(unstable_dev): Provide an option for unstable_dev to perform the check that prompts users to update wrangler, defaulting to false. This will prevent unstable_dev from sending a request to NPM on startup to determine whether it needs to be updated.#4179
dd270d00
Thanks @matthewdavidrodgers! - Simplify secret:bulk api via script settingsFiring PUTs to the secret api in parallel has never been a great solution - each request independently needs to lock the script, so running in parallel is at best just as bad as running serially.
Luckily, we have the script settings PATCH api now, which can update the settings for a script (including secret bindings) at once, which means we don't need any parallelization. However this api doesn't work with a partial list of bindings, so we have to fetch the current bindings and merge in with the new secrets before PATCHing. We can however just omit the value of the binding (i.e. only provide the name and type) which instructs the config service to inherit the existing value, which simplifies this as well. Note that we don't use the bindings in your current wrangler.toml, as you could be in a draft state, and it makes sense as a user that a bulk secrets update won't update anything else. Instead, we use script settings api again to fetch the current state of your bindings.
This simplified implementation means the operation can only fail or succeed, rather than succeeding in updating some secrets but failing for others. In order to not introduce breaking changes for logging output, the language around "${x} secrets were updated" or "${x} secrets failed" is kept, even if it doesn't make much sense anymore.
Patch Changes
#4402
baa76e77
Thanks @rozenmd! - This PR adds a fetch handler that usespage
, assumingresult_info
provided by the endpoint containspage
,per_page
, andtotal
This is needed as the existing
fetchListResult
handler for fetching potentially paginated results doesn't work for endpoints that don't implementcursor
.Fixes #4349
#4337
6c8f41f8
Thanks @Skye-31! - Improve the error message when a script isn't exported a Durable Object classPreviously, wrangler would error with a message like
Uncaught TypeError: Class extends value undefined is not a constructor or null
. This improves that messaging to be more understandable to users.7fbe1937
Thanks @jspspike! - Change local dev server default ip to*
instead of0.0.0.0
. This will cause the dev server to listen on both ipv4 and ipv6 interfacesf867e01c
Thanks @tmthecoder! - Support for hyperdrive bindings in local wrangler dev7e05f38e
Thanks @jspspike! - Fixed issue withtail
not using proxy0453b447
Thanks @maxwellpeterson! - Allows uploads with both cron triggers and smart placement enabled#4437
05b1bbd2
Thanks @jspspike! - Change dev registry and inspector server to listen on 127.0.0.1 instead of all interfacesUpdated dependencies [
4f8b3420
,16cc2e92
,3637d97a
,29a59d4e
,7fbe1937
,76787861
,8a25b7fb
]:Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.